SPACE 1/SPACE - Library 1 - Volume 1.iso/telecomm/532/frzdterm/read.me

Text File | 1991-12-24 | 19KB | 346 lines

READ.ME
==== ==

                       The FreeZe Dried Terminal v2.04
                       --- ------ ----- -------- -----

    I. Quick Setup of FzDSTerm to your system ................ [SET]
   II. New Stuff ............................................. [NEW]
  III. Use of the New .KEYs .................................. [KEY]
   IV. What You Might Find in Future Versions ................ [FUT]
    V. A Short Note To Reviewers ............................. [REV]


------------------------------------------------------------------------------

[SET] - Quick Setup
        ----- -----



     If you have a configuration file from Version 2.03 or below and are
either using monochrome or are on a TT, please delete your current config
file (FZDSTERM.CFG).  Also, if you delete your config, FzT has the new
protocols installed as defaults.  If you keep your config, you will need to
install these protocols by hand.

Follow these steps to quickly configure FzDSTerm to your system and create a
configuration (FZDSTERM.CFG) file: (Most of the options have presets, if these
are not suitable to your tastes or needs, feel free to change them.)


1.  If you do not have a Hard Drive, you may wish to use a RAM Disk as a fast
    drive which FzDSTerm will use to keep the protocols and other temporary
    files for increased productivity.  If you want to use this feature,
    install a RAM Disk now.  (HRAMDISK.PRG is recommended for this.)
2.  Run FZDSTERM.PRG
3.  It will pop up a fileselector asking you to locate the config file.
    Since you currently don't have one, click on Cancel.
4.  An alert box will appear telling you that it couldn't find the config
    file and that it will be using defaults.  Hit return.
5.  Another alert box will ask you what type of modem to set up for.  If you
    have a 300, 1200, or 2400 baud modem click on "Generic 2400".  If you have
    a USR HST or similar high-speed modem click on "USRobotics HST".
6.  A Quick Setup menu will appear next.  This is where you can set all of
    your defaults before you begin using FzT:
7.  It will default to 2400 baud, 8 bits, No Parity, 1 stop bit, No CTS/RTS,
    No XON/XOFF, Full Duplex, No Echo, No Linefeeds, Capture Open, VT-52
    Emulation.  If you need to change any of these, click on RS-232 config
    and do so.  Click on EXIT when you are done.8.  a) Click on Default
    Paths.  You may specify specific paths for most different types of
    files.  Click on a path to change it.  I prefer to make seperate paths
    for everything, I like to be organized, but you may
    leave them all to the default.
    b) If you are without a Hard Drive and have decided to use a RAM Disk as
    a fast drive, you will need to install it.  Click on "Ramdisk" and when
    the fileselector appears, move to the path for the RAM Disk in the
    fileselector, and click on "OK".
    c) Hit UNDO or the right mouse button when you are done.
9.  a) Click on Initialization strings.
    b) Next, use the arrow keys to move to the Current Area Code. If you are
    in the US or Canada, enter your current area code.
    If you are not, LEAVE THIS BLANK!  THIS IS IMPORTANT!!!
    c) If you are in the US or Canada, and your phone number is in the
    format of (xxx) yyy-zzzz, where (xxx) is your Area Code, you may wish to
    use the locked format dialing system in FzT.  This is best for people
    who don't dial internationally, and don't need to change modem settings
    for different BBSes.  FzT will default to "Free format", if you feel
    that the locked format is more suited toward your needs, select "Free
    Format Phone", and hit Return twice to skip through the conversion
    dialogs.
    d) If you want to change any of the preset Init strings, do so.  When
    you are done, click on EXIT.
10. Click on Save Config to write your configuration to the current path, and
    then EXIT to go on.
11. You will be presented with the Main Menu.  Enjoy!

------------------------------------------------------------------------------

[NEW] - Whats New?
        ----- ---
v2.10
-----

o The .KEY system has been adopted.  Please read the next section for
  details.
o The Monochrome interface has been completely redone.  I believe
  there will be no more problems with reading or using FzT in monochrome.
  I'm sorry for any in convience this may have caused any of you.
o The scrollback has been redone.  Many more options are now included under
  the text editor style drop down menus.
o An "Auto Learn Logon" feature has been included.  With it, creating
  autologon sequences requires only a click of the mouse, and to log on to a
  BBS by hand one last time.  It will fill in rest for you.
o The speed of input processing has again been substantially increased.  The
  autologs and automacros should slow down the system much less.
o The speed of loading a text file into the text editor should be increased
  substantially.
o An option has been included to disable the 1k Serial port output buffer
  which FzT usually installs.  This seems to solve any problems with
  uploading using HSTs and Zmodem/Ymodem-G.  (In RS-232 Config.)
o The maximum size of the text editor and scrollback has been increased to
  32,000 lines.  Although I do NOT recommend taking them up that far, it is
  there if you need it.
o A change has been made in the way FzT uses its memory.  This SHOULD solve
  any problems with bombing.
o An option has been added to ASCII send.  If you select "Begin Send", it
  will not include the Prefix.  If you select "Send Quoted", it will.
  (Previously to disable the Prefix, you had to delete the Prefix.)
o After selecting the path for the ramdisk, you will now be asked if you
  wish to copy the Protocols, the Archivers, or both in the RamDisk at
  startup.  (To conserve space in the ramdisk and time.)
o Mouse controlled scrolling has been added to both the scrollback and text
  editor.
o The editors for the Autodialer and Init Strings have been (finally!)
  redone.  You may now use the arrow keys to go back into a line.  (Instead
  of backspacing over the line to change something.)  A button ("Edit")
  has been added to the autodialer which selects whether the cursor keys
  control the red selection bar or the edit cursor.
o The Jump to Accessories feature has been improved.  A small oversight on my
  part has in the past caused the mouse cursor to behave very strangely when
  selecting options under the menu bar.
o In Init Strings, there is a button labelled "Char Delay", which allows you
  to specify a pause between characters when sending a dial command or init
  string to the modem.  This should help some modems recognise commands sent
  by FzT.
o When you have the "Auto Change Baud" option turned off and "No Dial While
  CD" selected, FzT will now connect when carrier detect goes on while
  dialing.  For some modems (HSTs), the CD goes on much in advance of the
  "CONNECT ..." response.  This will keep FzT from aborting the dial before
  the modem sends the "CONNECT".
o A Print feature has been added to the autodialer, and might come in handy.
o A new font has been put in, and the way FzT handles the fonts has been
  changed.  You may now use the selected font in any menu that uses the TOS
  font.
o Quite a few bug fixes, and I'm sure there are features which I have left
  out.

v2.04 Demo
----- ----

o A Beta-Test version of the FreeZe Dried Protocols has been included, and
  the default setup is included in FzDSTerm.  (These protocols will
  eventually become an internal part of FzDSTerm, once perfected.)  See
  FZDSXFER.DOC for more information.
o In the autodialer, an option has been added to allow you to enter any
  combination of characters in the Phone Number field.  This should fix any
  problems regarding the autodialer and international calling.  (You may
  toggle this feature in the Init Strings/Dialer Setup menu.)
o The speed of the ANSI processing has been improved somewhat.  Through my
  (inaccurate) speed tests, I calculate that FzDSTerm should be able to
  process between 1,700 and 2,300 bytes of ANSI per second, depending upon
  what is being displayed.  (This is with no other options enabled, besides
  autostart ZModem, using Turbo ST v1.84.)
o Many cosmetic bugs have been fixed in Monochrome.  Also, the color sliders
  have been replaced in mono with a large button allowing you to switch the
  foreground and background colors.
o A bug in the default paths/ramdisk initialization made putting the
  protocols and archive tools in anything but the main directory not function
  if a ramdisk was not installed.
o For TT Users: I have found some TTs where the carrier detect status is
  reversed from normal, and some where it is not.  When first creating a
  config file, FzT will ask you the current status of your modem's carrier
  detect.  From this, it will determine whether or not your TT's CD is
  reversed.  (If anyone can offer a reason or explaination for this, let me
  know.)

------------------------------------------------------------------------------

[KEY] - The New .KEY System
        --- ---  --- ------

     I have completely changed the way in which FzT checks for registration.
Previously, the registration information was an internal part of the
program.  This meant that all updates had to come from me, and also that to
generate a registered copy, it was quite a hassle for both the users and
myself.

     As of the registered version of 2.04 (not the demo version), this has
changed.  Now the registration info is kept in a seperate file, called a
Key.  This is the "key" to "unlock" the features of FzT.  This key is loaded
upon each bootup of FzDSTerm and its format is checked.  If it is valid, all
of the features which are disabled in the demo are available to you.  This
makes it much easier for you to get and use the latest version.  All you
have to do is download it from your local BBS and put it in the same
directory as your .KEY.

     Starting with version 2.10, the demo and registered versions of the
program for everyone will be exactly the same.  The main advantage of this
is that I can distribute the registered version everywhere, and only the
people who have the .KEYs (who have paid) may use some of the features.  I
will send you the .KEY, and when the next version comes out instead of
having to get it from me, you can use your current .KEY on the new version.
This is faster for you, and less of a headache for me.

     The .KEY contains your name, address, phone number, serial number, etc.
Much of this information is displayed when you first load FzT and when you
click on the FzDS symbol on the main menu.  I advise you to not give out
your .KEY as it can easily be traced back to you by anyone.  Its easy for you
to check who a particular .KEY belongs to, and if its not yours, you are
expected not to use it.


How to set up the .KEY for FzDSTerm versions 2.04 Rel and above:

1. Rename your .KEY to FZDSTERM.KEY, if it is not already.
2. Rename the program to FZDSTERM.PRG.
3. Put the .KEY in the same path as your FZDSTERM.CFG (usually also with the
   FZDSTERM.PRG.)
4. Run FzDSTerm

If for some reason it tells you "KEY Not Valid! Please obtain a new one.",
your KEY is not valid with that version of FzT.  Contact me to get a new
one.  (You may either send for the $5 upgrade or call Hitchhiker's Guide To
the Galaxy, the main FzDSTerm support board, and I will F-mail it to you.)
I will try to make your .KEY work with all future versions, but I may be
forced to change the format if some people don't follow the rules.


I would like you to adhere to a few simple rules regarding .KEYs:

1. One .KEY may either be used by one user on multiple systems, or by
   multiple users on one system.  Under no circumstances is a single key
   to be used by multiple users on multiple systems.

2. Under no circumstances may a .KEY be copied or archived except for backup
   purposes and to set FzT up on another system you SOLELY will be using.
   Transmitting (uploading) a .KEY anywhere for any reason is not allowed,
   except from me and to me on Hitchhiker's Guide.  You may copy, archive, or
   transmit all other files except the .KEY and the registered versions of
   FZDSTERM.PRG v2.04 and below.

3. If I EVER find or hear about a "cracked" .KEY (one not generated by me,
   containing bogus registration info), I reserve the right to either:
     a. Immediately change the format of the .KEYs, causing all registered
        users to have to get new .KEYs.
     b. Go back to the old method, taking away this great way of operation.
        If people can't repect my right to only allow people to use all
        parts of FzT only if they've registered, I don't see why I should
        make it any easier for them.

4. If I ever find someone giving out their .KEY to other people, I will
   cancel their registration and make their .KEY invalid for future versions
   of FzDSTerm.  If they want to be eligible for upgrades, they will have to
   pay again.  If I feel that their .KEY has been spread around too much, I
   may choose to do any of the following under #3.

NOTE: If you ever come across a .KEY that is not yours; send it to me, and I
      will make it worth your while.  I would like to know if a key is being
      spread around.  Either print a Hex dump of it and mail it to me, or send
      it to me on Hitchhikers.a

------------------------------------------------------------------------------

[FUT] - What You Might Find in Future Versions:
        ---- --- ----- ---- -- ------ --------

        On the continual quest to perfect the FreeZe Dried Terminal, I plan
to slowly add and change it to be able to handle everyone's needs.  The
following is a list of features which you might see later on:

o Much improved documentation.  I realize that the main documentation
  (FZDSTERM.DOC) in its present form does not help many people out with the
  complicated features of FzT.  I have had several offers by people to write
  documentation for me, and I am having them submit a sample of the rewritten
  docs for me to compare.  I am willing to offer a bit in return for this, if
  you are interested in trying out.
o VT-100, VT-102, VT-2xx, and VT-3xx emulations.  I have had many requests
  for these.  I have limited documentation on VT-100, but am looking for
  more.Please send me and documentation you may have on them!
o If you like the FZDSXFER.TTP protocols, you should look forward to their
  improvement.  We plan on adding Zmodem, among other things to the list of
  protocols.  If they get to a point where I no longer include XYZ.TTP in the
  distribution, I will make them an internal part of FzT.  (Extra slots for
  external protocols will always be available.)  Please send me any
  documentation you may have on Z-Modem.
o Look forward the Instant Graphics emulation being improved.  At the moment,
  the IGS in FzT is faster, but does only the graphics at the moment.  Many
  of the extended commands and sounds are not currently supported.  (I should
  be getting the data for the sounds from Larry Mears, the author of IGS.ACC
  and IGS.EMU.)
o The .DO Script files can be added to.  If you would like to see them
  improved or a command added, let me know.
o Background Transfers.  We have been optimising the protocols for
  efficiency, and once we get them done, I will be willing to make them an
  .ACC, and run in the background.  I believe this should be a nice addition,
  but I can give no guarantees on this one.
o Background Dialing.  If anyone really wants this, I can do it.  There are
  two choices for this:  Either internal in FzT, or an ACC.  If its internal,
  it will rely on the user interface routines for its timing.  This means
  that it will stop dialing if you run an external program or you get stuck
  in some GEM somewhere (Fileselector, GEM Alert Box, etc.)  If its an ACC,
  it will require an accessory slot, and you will be able to use it as long
  as you are either in FzT or a GEM program.
o TT Resolution support.  If I can find some specs on the TT Rezes I might be
  able to do TT Medium and 16 color ANSI.  There are no guarantees on this
  either.


------------------------------------------------------------------------------

[REV] - A Short Note To Reviewers:
        - ----- ---- -- ---------

I would like to say something to anyone wanting to write a major review of
The FreeZe Dried Terminal for the general public, such as an online magazine
or other publication.  Doubtless, you will end up comparing FzDSTerm against
the capabilities of another program.  Please keep in mind that even though
you may have a TT030 with one of the new graphics boards sitting on your
desk, the majority of the "general public" who the review is directed toward
will be using stock STs.
     I believe I have taken raw materials and peiced them together to form a
very good product.  I own an 8Mhz 520ST with a 2.5 meg upgrade, color monitor,
and hard drive.  With those resources, I have come up with what I believe
to be the finest terminal program available for the ST.  I do not own a
monochrome monitor, a TT, or a graphics card.  FzDSTerm was written on my
system, and it shows tremendously.  Monochrome was added as an afterthought,
and I have not been able to see for myself what it looks like, as I cannot
get ahold of a mono monitor.  It does not run in a window or as an accessory,
because terminals of this type simply cannot properly handle high speed
transmissions on a stock ST.
     You may question my reasoning behind not using GEM, as its built into
the operating system and everything else uses it, so why don't I?  There are
many things I could say for this, but I don't really know for myself.  If you
boot up FzDSTerm in ST color and look at the main menu, perhaps this will
answer your question.  In my opinion, it looks much better than GEM, is
faster, and more flexible.  No matter what anyone says to me, GEM uses >2<
colors.  None of the buttons, alert boxes, or dialog borders use anything but
BLACK and WHITE.  Sure, dialogs can have a background fill pattern that is in
color, but this really doesn't appeal to me as fully using the capabilities
of the ST.  My interface currently doesn't completely support device
independant graphics, but I don't have anything but ST color so I couldn't
test anything even if I did attempt to make it do so.  I don't have a TT, its
that simple.
     If you plan on comparing FzDSTerm with the capabilities of another
program, all I ask is this.  Give it a fair comparison, and use FzDSTerm on
an ST in medium resolution along with the other program using the same
setup.  Don't complain about how horrible the graphics look in monochrome and
turn around and say how great some other program will multitask on the TT.
You would neglect to mention that this other program cannot correctly display
ANSI and cannot "multitask" or handle high-speed modems on an ST because it
runs so slowly.

------------------------------------------------------------------------------